Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(scale): upgrade d3-time to v2.4 for d3-scale compatibility #1219

Merged
merged 3 commits into from
May 19, 2021

Conversation

Pringels
Copy link
Contributor

@Pringels Pringels commented May 18, 2021

The latest minor version 3.3.0 of d3-scale makes use of utility functions exposed by d3-time version 2.1.0 (see: d3/d3-scale@80ff9b2#commitcomment-50668715)

This makes d3-scale 3.3.* incompatible with d3-time 1.x or even 2.0.0

The latest minor version `3.3.0` of `d3-scale` makes use of utility functions exposed by `d3-time` version `2.1.0` (see: d3/d3-scale@80ff9b2#commitcomment-50668715)

This makes `d3-scale` 3.3.* incompatible with `d3-time` `1.x` or even `2.0.0`
Copy link
Collaborator

@williaster williaster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix @Pringels 🙏 Bummer about the breaking minor version bump. I had one comment that hopefully will get the build working.

packages/visx-scale/package.json Show resolved Hide resolved
@williaster williaster changed the title deps: upgrade d3-time to v2.4 fix(scale): upgrade d3-time to v2.4 for d3-scale compatibility May 19, 2021
Copy link
Collaborator

@williaster williaster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again @Pringels! 💯

@williaster williaster merged commit 526b5aa into airbnb:master May 19, 2021
@github-actions
Copy link

🎉 This PR is included in version v1.11.1 of the packages modified 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants